Skip to main content

Interoperability Rules

Layer Dependency Rules​

  • Dependencies flow downward only.
  • A layer must not require any specific app.
  • A layer must not require any specific vendor.
  • A layer must be able to degrade safely when adjacent layers fail.

Inter-Layer Contracts​

Each layer must declare:

  • What it requires from layers below
  • What it guarantees to layers above
  • What it must never assume about other layers

Portability Requirements​

  • Identity must be portable across apps and services.
  • Data containers must be portable across storage providers.
  • Assets must remain valid even if an exchange or marketplace disappears.
  • Applications must not be the source of truth for identity, data, or assets.

Replaceability Requirements​

  • A compliant replacement service must be able to re-implement a layer without rewriting higher layers.
  • Migration must not require permission from the previous provider.